Dynomotion

Group: DynoMotion Message: 807 From: cell.vlad Date: 12/22/2010
Subject: KFlop/KMotion software related questions
Hello Group!

I am currently working on retrofitting an old Lagun FTV1 to CNC mill, using steppers and KFlop controller.
Great controller! Fast and reliable command handling.
Before I try to use parallel port controller and Mach3 combination, but always see timing issues in the driver response. With KFlop all smooooth!  Great Job!

However, working with KFlop and PC software (v.4.23), I found a few confusing issues, and trying to resolve them:

1) There is any way to change description of the Bits on the Digital I/O Screen ?  All descriptions is confusing and take some time to recall what is connected and how...  I suggest to have an DigitalIOInit file, where all "name" variables is described and would be easy configured.  Or I missing something? Please help.

2) There is any description available, except Help screens and KFlop documentation, described a difference between "Channel" / "Channels" / "Chan" in the Configuration and FLASH Screen. It is a "special" language or it is just added for confusion or I just not seen something...  I think it shall be some kind of "Ideology" document, describing the "Channel"/"Channels"  conception in conjunction with another "Channels"...  Or perhaps Dyno plan to remove that confusion, by using a different terminology, for instance "Group" / "Channels" or some thing in that nature.   Please advise.

2.a) related to above - For given "Channel" there is possible to select a specific Output Chan and Input Chan other then pairs (0-1, 2-3, etc...) ?  What is done for?  and How I can use ?

3) Where is a Input/Output "Bit" word forming list described anywhere?  In Digital I/O Screen you can see a "Bit" in use, but there is no such document or Help screen ( at least I could not find ) where all "Bit" strategy is described clearly... Please point in right direction.

4) When you open KMotion on PC, a nice logo on full screen is displayed.  Do any body could describe the reason to have it on full screen ?   And how this screen is used except to use menu on the top?  This screen is confusing and have no practical needs BMHO.  It is annoying to do resizing screen all time when you open on desktop and have no practical use of it.  For instance a Console would be appropriate to have all time open on that screen.  Or, for instance, a status screen and "GetStatus" HEX screen or LED type of screen where all IO "Channels" would be displayed with their respected activity, etc...   Please explain.

5) Console - How would be possible to use Console with 6 fold-down menu in more practical manner?  For instance would be nice to have a history on that folddowns or associated set of commands...  That history set of commands would be nice to store in an external file by default and have way to edit or change as needed, with "stick" function for instance...

6) I/O with LVTTL - would be nice to have a suggested diagram conversion from 5v (TTL) or 12v, to/from LVTTL, since it is not a simple issue.  Will explain.  If conversion done incorrectly, a nose on the "0" level would be "amplified" and cause significant problem on overall system stability issue. For instance it could be one of the issue for incorrect encoder reading or axes run-out, or sudden stop on the Limit signal...  Same would be concern for grounding and suggested cabling.

Nevertheless, KFlop still great product!   I even see a direct way to use KMotionCNC directly, without Mach3.  It is very straight forward and do the job.

Thank you for the efforts!

Vlad
Group: DynoMotion Message: 811 From: Tom Kerekes Date: 12/22/2010
Subject: Re: KFlop/KMotion software related questions
Hi Vlad,
 
Thanks for all the detailed feedback.  We appreciate it and will consider all the suggesions.
 
No we don't currently have a means for Users to change the bit labels on the Digital I/O screen.
 
Sorry about over using the term "channel".  The main concept is that there are Axis Channels and there are Device (DACS, ADC, Step/Dir, Full Bridges, et) Channels.  The Axis Channels are entities at a higher level and each axis can be configured to use one or two input and/or output devices.  So for example motion comands can be made to an axis channel which in turn will use various input and output devices.
 
In some modes two input or output devices are used and are not required to be consecutive channels.  For example resolvers require 2 ADC input channels that are not required to be consecutive.
 
Thanks
TK

Group: DynoMotion Message: 812 From: cell.vlad Date: 12/23/2010
Subject: Re: KFlop/KMotion software related questions
Tom,
Thank you for explanation on "Axis Channel" - it is make sense since there is hardware limitations to use a MUX.   Would be nice to have that described in the Help or some kind of accompany document.  Just suggestion.

I still have troubles with I/O BIT determination:
> 3) Where is a Input/Output "Bit" word forming list described anywhere?  In
> Digital I/O Screen you can see a "Bit" in use, but there is no such document or
> Help screen ( at least I could not find ) where all "Bit" strategy is described
> clearly... Please point in right direction.


Also, do you have a suggestions for LVTTL  I/O circurits?
> 6) I/O with LVTTL - would be nice to have a suggested diagram conversion from 5v
> (TTL) or 12v, to/from LVTTL, since it is not a simple issue.  Will explain.  If
> conversion done incorrectly, a nose on the "0" level would be "amplified" and
> cause significant problem on overall system stability issue. For instance it
> could be one of the issue for incorrect encoder reading or axes run-out, or
> sudden stop on the Limit signal...  Same would be concern for grounding and
> suggested cabling.

 
Looking in to details, I appreciate size of the project.  Great Job!

Thanks,
Vlad